Imanol Pardavila
2011-Jul-16 00:57 UTC
[asterisk-users] Unable to register an endpoint after upgrading from 1.4.2.20 to 1.8.3.1
Hello, I've just upgrade from 1.4.2.20 to 1.8.3.1 and some kind of endpoint aren't able to register. Message is: [Jul 16 01:26:15] NOTICE[25443]: chan_sip.c:23511 handle_request_register: Registration from '<sip:user637801>' failed for 'X.X.X.X:5060' - No matching peer found sip.conf [user637801] type=friend context=FROMuser637805 host=dynamic secret=password dtmfmode=rfc2833 disallow=all allow=g729 allow=ulaw allow=alaw nat=yes canreinvite=no call-limit=2 REGISTER sip:Y.Y.Y.Y SIP/2.0. From: <sip:user637801>;tag=e00028-c0a800fd-13c4-50029-508b5-41d85fb5-508b5. To: <sip:user637801>. Call-ID: e162cc-c0a800fd-13c4-50029-508b5-18c6cea7-508b5. CSeq: 2 REGISTER. Via: SIP/2.0/UDP 192.168.100.2:42904;branch=z9hG4bK-508b5-13aa048e-5ff4a5b9. Max-Forwards: 70. Expires: 60. Authorization: Digest username="user637801",realm="asterisk",nonce="7bf18d37",uri="sip:Y.Y.Y.Y",response="ce8847cf30a69e1c7735de86a82c3e6e",algorithm=MD5. Contact: <sip:987987987 at 192.168.100.2:42904>. Content-Length: 0. SIP/2.0 100 Trying. Via: SIP/2.0/UDP 192.168.100.2:42904;branch=z9hG4bK-508b5-13aa048e-5ff4a5b9;received=X.X.X.X. From: <sip:user637801>;tag=e00028-c0a800fd-13c4-50029-508b5-41d85fb5-508b5. To: <sip:user637801>. Call-ID: e162cc-c0a800fd-13c4-50029-508b5-18c6cea7-508b5. CSeq: 2 REGISTER. Server: ASTERISK. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH. Supported: replaces, timer. Content-Length: 0. SIP/2.0 403 Forbidden (Bad auth). Via: SIP/2.0/UDP 192.168.100.2:42904;branch=z9hG4bK-508b5-13aa048e-5ff4a5b9;received=X.X.X.X. From: <sip:user637801>;tag=e00028-c0a800fd-13c4-50029-508b5-41d85fb5-508b5. To: <sip:user637801>;tag=as710c9007. Call-ID: e162cc-c0a800fd-13c4-50029-508b5-18c6cea7-508b5. CSeq: 2 REGISTER. Server: ASTERISK. Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY, INFO, PUBLISH. Supported: replaces, timer. Content-Length: 0. I think the problem is that REGISTER packet has: sip:user637801, instead of sip:user637801 at Y.Y.Y.Y This works in 1.4 version but not in 1.8; it maybe more restrict? I can't add @Y.Y.Y.Y in end point's configuration; is there any option to put in peer configuration to allow this registration? Thanks Imanol