Summary: | ASTERISK-10059: All SIP peers stuck with Canreinvite=no | ||
Reporter: | Sam Deller (samdell3) | Labels: | |
Date Opened: | 2007-08-09 16:42:46 | Date Closed: | 2007-08-09 17:35:44 |
Priority: | Minor | Regression? | No |
Status: | Closed/Complete | Components: | Core/General |
Versions: | Frequency of Occurrence | ||
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Upgraded from 1.4.5 to 1.4.10, low and behold, all sip re-invites stopped working with no change to config files. Cannot locate any documentation, bugs or changelogs as to maybe if this is a change in behaviour or what. But no matter what we do, we can only ever see 'canreinvite = no' for 'sip show peer xxxx', even with every sip peer, and sip.conf [general] set to canreinvite=yes. EVERY call now says Packet2Packet Bridging instead of Native Bridging as they used to, so its not just an error in the sip show peer output. ****** ADDITIONAL INFORMATION ****** SIP.CONF: [general] bindport=5060 bindaddr=0.0.0.0 context=guest disallow=all allow=ulaw:30 transfer=no cancallforward=no canreinvite=yes sendrpid=yes trustrpid=no progressinband=yes t38pt_udptl=yes t38pt_rtp=no t38pt_tcp=no rtptimeout=60 checkmwi=120 [66500012] type=friend insecure=port,invite port=5060 qualify=yes host=dynamic dtmfmode=RFC2833 md5secret=4f5cd4f8d85bd9064a4300252276b15f nat=no mailbox=066500012 canreinvite=yes context=default CLI> sip show peer 66500012 **EDIT CanReinvite : No **EDIT | ||
Comments: | By: Mark Michelson (mmichelson) 2007-08-09 17:35:27 See issue ASTERISK-10056. |