Summary: | ASTERISK-28305: register_aor_core: Unable to bind contact | ||
Reporter: | Ateen Chaughule (ateenc) | Labels: | pjsip |
Date Opened: | 2019-02-25 13:38:27.000-0600 | Date Closed: | 2019-02-25 13:43:57.000-0600 |
Priority: | Minor | Regression? | |
Status: | Closed/Complete | Components: | pjproject/pjsip |
Versions: | 15.4.0 | Frequency of Occurrence | One Time |
Related Issues: | |||
Environment: | Attachments: | ||
Description: | Hello,
I was trying to include UPDATE and 100rel to the call flow from asterisk I used the python script to create pjsip.conf. I have not made change to any other file, except extension.conf and added the PJSIP to the TN i need to make the call from . But i get the following error cannot bind the TN Connected to Asterisk 15.4.0 currently running on astrisk-domestic (pid = 6612) -- Attempted to remove non-existent contact 'sip:+14629591001@144.60.212.81:5060' from AOR '+14629591001' by request [2019-02-25 13:28:35] WARNING[6655]: db.c:348 ast_db_put: Couldn't execute statment: SQL logic error [2019-02-25 13:28:35] ERROR[6655]: res_pjsip_registrar.c:637 register_aor_core: Unable to bind contact 'sip:+14629591001@144.60.212.81:5060' to AOR '+14629591001' == Setting global variable 'SIPDOMAIN' to '144.60.212.76' -- Executing [6166310017@LocalSets:1] Dial("PJSIP/+14629591001-00000000", "SIP/vISBC/6166310017") in new stack == Using SIP RTP CoS mark 5 [2019-02-25 13:28:41] ERROR[6691][C-00000001]: chan_sip.c:4274 __sip_reliable_xmit: Serious Network Trouble; __sip_xmit returns error for pkt data -- Called SIP/vISBC/6166310017 == Spawn extension (LocalSets, 6166310017, 1) exited non-zero on 'PJSIP/+14629591001-00000000' -- Executing [h@LocalSets:1] Dial("PJSIP/+14629591001-00000000", "SIP/vISBC/h") in new stack -- Caller hung up before dial. == Spawn extension (LocalSets, h, 1) exited non-zero on 'PJSIP/+14629591001-00000000' MY PJSIP.CONF file [transport-udp] type = transport protocol = udp bind = 0.0.0.0 [+14629591001] type = aor max_contacts = 1 [+14629591001] type = auth username = +14629591001 password = 288Labs [+14629591001] type = endpoint context = LocalSets dtmf_mode = none disallow = all allow = ulaw timers = no timers_sess_expires = 3800 direct_media = no send_pai = yes inband_progress = yes auth = +14629591001 outbound_auth = +14629591001 aors = +14629591001 EXTENSION.CONF exten => 4629591001,1,Dial(PJSIP/+14629591001) same => n,Hangup() | ||
Comments: | By: Asterisk Team (asteriskteam) 2019-02-25 13:38:28.090-0600 Thanks for creating a report! The issue has entered the triage process. That means the issue will wait in this status until a Bug Marshal has an opportunity to review the issue. Once the issue has been reviewed you will receive comments regarding the next steps towards resolution. A good first step is for you to review the [Asterisk Issue Guidelines|https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines] if you haven't already. The guidelines detail what is expected from an Asterisk issue report. Then, if you are submitting a patch, please review the [Patch Contribution Process|https://wiki.asterisk.org/wiki/display/AST/Patch+Contribution+Process]. Please note that once your issue enters an open state it has been accepted. As Asterisk is an open source project there is no guarantee or timeframe on when your issue will be looked into. If you need expedient resolution you will need to find and pay a suitable developer. Asking for an update on your issue will not yield any progress on it and will not result in a response. All updates are posted to the issue when they occur. By: Asterisk Team (asteriskteam) 2019-02-25 13:38:29.346-0600 We appreciate the difficulties you are facing, however information request type issues would be better served in a different forum. The Asterisk community provides support over IRC, mailing lists, and forums as described at http://asterisk.org/community. The Asterisk issue tracker is used specifically to track issues concerning bugs and documentation errors. If this issue is actually a bug please use the Bug issue type instead. Please see the Asterisk Issue Guidelines [1] for instruction on the intended use of the Asterisk issue tracker. Thanks! [1] https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines By: Asterisk Team (asteriskteam) 2019-02-25 13:38:59.328-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Asterisk Team (asteriskteam) 2019-02-25 13:52:55.444-0600 This issue has been reopened as a result of your commenting on it as the reporter. It will be triaged once again as applicable. By: Joshua C. Colp (jcolp) 2019-02-25 13:56:26.895-0600 Please use the information resources at hand to ensure that this is a bug before filing here. As well the version of Asterisk you are using is no longer supported. |