Hello, I habe the following problem when re-registering to an external SIP provider during a call which results in immediate call-hangups. - FS re-registers with nonce - 2ms later FS re-registers without nonce - external SIP provider asks for credentials - FS re-registers with nonce - External provider hangs up call I think the external equipment (Huawei) gets his messages into disorder and then hangs up. My question is: How can I force FS to only register once (without nonce)? As said, FS tries to register twice within 2 msecs without receiving an answer in between. FS is on a public IP, so there are no NAT problems expected (I can see that until the re-register takes place, media is passed in both directions). Best regards Peter See log: U 2009/05/07 15:04:37.441636 217.xxx.xxx.190:5080 -> 213.xxx.xxx.2:5060 REGISTER sip:sip.provider.de;transport=udp SIP/2.0. Via: SIP/2.0/UDP 217.xxx.xxx.190:5080;rport;branch=z9hG4bK43088Ha5QpZBN. Max-Forwards: 70. From: <sip:0123456779@sip.provider.de;transport=udp>;tag=jSFF9XmFZ50pp. To: <sip:0123456779@sip.provider.de;transport=udp>. Call-ID: a0364af0-3b05-11de-bc92-f9fefd954b7b. CSeq: 114732262 REGISTER. Contact: <sip:gw+XXX_01234@217.xxx.xxx.190:5080;transport=udp>. Expires: 0. User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-13231M. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO. Supported: timer, precondition, path, replaces. Authorization: Digest username="0123456779", realm="provider.de", nonce="4a02dc5ba90f927c74161f89e7550138b93f12cc", cnonce="y8SXDLWpEiyNPQAekEzDTg", algorithm=MD5, uri="sip:sip.provider.de;transport=udp", response="1d44f64eec5a5b38b44e398dea201a08", qop=auth, nc=00000002. Content-Length: 0. . # U 2009/05/07 15:04:37.443395 217.xxx.xxx.190:5080 -> 213.xxx.xxx.2:5060 REGISTER sip:sip.provider.de;transport=udp SIP/2.0. Via: SIP/2.0/UDP 217.xxx.xxx.190:5080;rport;branch=z9hG4bK5ct1aDU8mZNyg. Max-Forwards: 70. From: <sip:0123456779@sip.provider.de;transport=udp>;tag=t1SNQpUB8cKcK. To: <sip:0123456779@sip.provider.de;transport=udp>. Call-ID: a0364af0-3b05-11de-bc92-f9fefd954b7b. CSeq: 114732402 REGISTER. Contact: <sip:gw+XXX_01234@217.xxx.xxx.190:5080;transport=udp>. Expires: 60. User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-13231M. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO. Supported: timer, precondition, path, replaces. Content-Length: 0. . # U 2009/05/07 15:04:37.466691 213.xxx.xxx.2:5060 -> 217.xxx.xxx.190:5080 SIP/2.0 401 Unauthorized. Via: SIP/2.0/UDP 217.xxx.xxx.190:5080;branch=z9hG4bK5ct1aDU8mZNyg;rport=5080. Call-ID: a0364af0-3b05-11de-bc92-f9fefd954b7b. From: <sip:0123456779@sip.provider.de;transport=udp>;tag=t1SNQpUB8cKcK. To: <sip:0123456779@sip.provider.de;transport=udp>;tag=702dbe10. CSeq: 114732402 REGISTER. Server: SIP Router. WWW-Authenticate: Digest realm="provider.de",nonce="4a02dd789a25b67f29ba21f65429d13c4bbc2ded",qop="auth". Content-Length: 0. . # U 2009/05/07 15:04:37.467211 217.xxx.xxx.190:5080 -> 213.xxx.xxx.2:5060 REGISTER sip:sip.provider.de;transport=udp SIP/2.0. Via: SIP/2.0/UDP 217.xxx.xxx.190:5080;rport;branch=z9hG4bK6NKtc8Bcj8BHc. Max-Forwards: 70. From: <sip:0123456779@sip.provider.de;transport=udp>;tag=t1SNQpUB8cKcK. To: <sip:0123456779@sip.provider.de;transport=udp>. Call-ID: a0364af0-3b05-11de-bc92-f9fefd954b7b. CSeq: 114732403 REGISTER. Contact: <sip:gw+XXX_01234@217.xxx.xxx.190:5080;transport=udp>. Expires: 60. User-Agent: FreeSWITCH-mod_sofia/1.0.trunk-13231M. Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, PRACK, MESSAGE, SUBSCRIBE, NOTIFY, REFER, UPDATE, REGISTER, INFO. Supported: timer, precondition, path, replaces. Authorization: Digest username="0123456779", realm="provider.de", nonce="4a02dd789a25b67f29ba21f65429d13c4bbc2ded", cnonce="dbAgB7WqEiyNPQAekEzDTg", algorithm=MD5, uri="sip:sip.provider.de;transport=udp", response="6a55b27caec6b06bd9da707e7b24d82b", qop=auth, nc=00000001. Content-Length: 0. . # U 2009/05/07 15:04:37.470935 213.xxx.xxx.2:5060 -> 217.xxx.xxx.190:5080 BYE sip:gw+XXX_01234@217.xxx.xxx.190:5080;transport=udp SIP/2.0. Via: SIP/2.0/UDP 213.xxx.xxx.2:5060;branch=z9hG4bK400739ec3ad9e5bbd7f5edccf. Call-ID: d0e38021-b5a9-122c-3d8d-001e904cc34e. From: <sip:0049987654321@sip.provider.de>;tag=31de8a21. To: "unknown"<sip:0123456779@sip.provider.de;transport=udp>;tag=K287aS5jveQ9H. CSeq: 1 BYE. Max-Forwards: 70. Content-Length: 0.
Looks like they are sending you a bye... not quite sure this is our problem. Can you provide a sip trace in pcap format for me to see? /b On May 7, 2009, at 8:37 AM, Peter P GMX wrote:
Hello,
I habe the following problem when re-registering to an external SIP provider during a call which results in immediate call-hangups. - FS re-registers with nonce - 2ms later FS re-registers without nonce - external SIP provider asks for credentials - FS re-registers with nonce - External provider hangs up call
I think the external equipment (Huawei) gets his messages into disorder and then hangs up.
My question is: How can I force FS to only register once (without nonce)? As said, FS tries to register twice within 2 msecs without receiving an answer in between. FS is on a public IP, so there are no NAT problems expected (I can see that until the re-register takes place, media is passed in both directions).
Best regards Peter
Brian West brian@freeswitch.org -- Meet us at ClueCon! http://www.cluecon.com
Also fix your evil mail server cuz I tried tried to email you and it bounced back. You have failed to detail your scenario more... options used .. how you connect things.. every detail counts no matter how small. Then collect it up and put it on Jira. /b On May 7, 2009, at 8:37 AM, Peter P GMX wrote:
Hello,
I habe the following problem when re-registering to an external SIP provider during a call which results in immediate call-hangups. - FS re-registers with nonce - 2ms later FS re-registers without nonce - external SIP provider asks for credentials - FS re-registers with nonce - External provider hangs up call
I think the external equipment (Huawei) gets his messages into disorder and then hangs up.
My question is: How can I force FS to only register once (without nonce)? As said, FS tries to register twice within 2 msecs without receiving an answer in between. FS is on a public IP, so there are no NAT problems expected (I can see that until the re-register takes place, media is passed in both directions).
Best regards Peter
Brian West brian@freeswitch.org -- Meet us at ClueCon! http://www.cluecon.com
Peter, Fix your email server I'm tired of my messages to you getting bounced back. Also upload cleaned up configs without all the comments and DO NOT attach tar.gz files. /b
participants (2)
-
Brian West
-
Peter P GMX