On 12/27/2011 01:43 PM, Jonas Kellens wrote:> Hello list,
>
> any idea why this call goes to the extension 3292000101 :
>
> /INVITE sip:3292000101 at IP.IP.IP.IP:5060 SIP/2.0
> Call-ID: OTRC74RLS5C2PBYULB3HSJZBR4 at IP.IP.IP.IP
> CSeq: 102 INVITE
> From: "32433885116" <sip:32433885116 at
IP.IP.IP.IP>;tag=74706
> Via: SIP/2.0/UDP
> IP.IP.IP.IP:5060;rport;branch=z9hG4bKcc90522a02bb6591fd8a807e66
> Via: SIP/2.0/UDP
> IP.IP.IP.IP:5060;branch=z9hG4bKd636e00c235e59dbb2d4a5eff83fdd96
> Max-Forwards: 68
> Content-Type: application/sdp
> Contact: <sip:32433885116 at IP.IP.IP.IP:5060;transport=udp>
> User-agent: Vox Callcontrol
> To: <sip:3292000101 at IP.IP.IP.IP>
> Content-Length: 309
> Record-Route: <sip:IP.IP.IP.IP:5060;lr>/
>
>
> and this call goes to the s-extension :
>
> /<--- SIP read from UDP:IP.IP.IP.IP:5060 --->
> INVITE sip:s at IP.IP.IP.IP:5060 SIP/2.0
> Record-Route: <sip:IP.IP.IP.IP;lr;ftag=as6aa259f4;did=949.96eeed57>
> Via: SIP/2.0/UDP IP.IP.IP.IP;branch=z9hG4bK918e.b1b09812.0
> Via: SIP/2.0/UDP
>
217.111.202.80:5060;received=217.111.202.80;branch=z9hG4bK5cb88830;rport=5060
> Max-Forwards: 69
> From: "32433885116" <sip:32433885116 at
217.111.202.80>;tag=as6aa259f4
> To: <sip:3292000101 at IP.IP.IP.IP>
> Contact: <sip:32433885116 at 217.111.202.80:5060>
> Call-ID: 092fd61b1e3aad5e670dfa94578db96d at 217.111.202.80:5060
> CSeq: 102 INVITE
> User-Agent: TLDOSIPS
> Date: Tue, 27 Dec 2011 19:26:35 GMT
> Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY,
> INFO, PUBLISH
> Supported: replaces, timer
> Content-Type: application/sdp
> Content-Length: 296/
>
>
> What is the difference ??
Did you look at the Request-URIs specified in the INVITE lines at the
beginning of the SIP messages? One specifies 's' as the target, the
other specifies '3292000101'.
--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming at digium.com | SIP: kpfleming at digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org