[asterisk-users] PJSIP issues with handling incoming calls

[Nick Awesome]

Thats because I call from one to other

here’s logs where I call from mobile

<--- Received SIP request (469 bytes) from UDP:80.75.132.66:5060 --->
ACK sip:s at pbx_ip_address:57408;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 80.75.132.66:5060;branch=z9hG4bK-524287-1-NGJlZjMxNThhYjI2YjI3Y2EyODE0MThhMTVkNjY0ZTA.--5c6da819e6300b26;rport
Max-Forwards: 70
To: <sip:73432260005 at 80.75.132.66>;tag=z9hG4bK-524287-1-NGJlZjMxNThhYjI2YjI3Y2EyODE0MThhMTVkNjY0ZTA.--5c6da819e6300b26
From: <sip:+79999823064 at 80.75.132.66>;tag=7ozmpvsvqs26kcor.o
Call-ID: 18e2786560719216837824k41099rmwp
CSeq: 586 ACK
Content-Length: 0


<--- Received SIP request (469 bytes) from UDP:80.75.132.66:5060 --->
ACK sip:s at pbx_ip_address:57408;transport=UDP SIP/2.0
Via: SIP/2.0/UDP 80.75.132.66:5060;branch=z9hG4bK-524287-1-YzhmMDE2NzE1YjRhOTM4NjQ1MjMxMmMyMmM0MWFiZTE.--be7c48325cdef400;rport
Max-Forwards: 70
To: <sip:73432260050 at 80.75.132.66>;tag=z9hG4bK-524287-1-YzhmMDE2NzE1YjRhOTM4NjQ1MjMxMmMyMmM0MWFiZTE.--be7c48325cdef400
From: <sip:+79999823064 at 80.75.132.66>;tag=yddmzvcoi3waw24e.o
Call-ID: 22e7064301970213226722k41100rmwp
CSeq: 588 ACK
Content-Length: 0

On 02 Sep 2014, at 15:01, Joshua Colp <jcolp at digium.com> wrote:

> Nick Awesome wrote:
>> Hello guys.
> 
> Kia ora,
> 
>> Have 2 external numbers that required registration on provider server,
>> 
>> trunk1: 734322600*05*@80.75.132.66
>> trunk2: 734322600*50*@80.75.132.66
>> 
>> Thing is I can’t figure out how to route them to different IVRs
>> 
>> by default Asterisk can’t match endpoint
>> 
>> Request from '<sip:+ 734322600*05*@80.75.132.66>' failed for
>> '80.75.132.66:5060' (callid: 50e9132765782741404408k2469rmwp) - No
>> matching endpoint found
>> 
>> Can’t set /identify /by IP because they got the same ip.
>> 
>> Is there way to configure asterisk so incoming calls from same IP but
>> different ID will use different contexts?
> 
> If the From header contains the destination number (as it seems to based on your above log message and config) you can create two different endpoints and match based on the user portion of the From header.
> 
> [734322600*05*]
> type=endpoint
> context=did-1
> disallow=all
> allow=ulaw
> 
> [734322600*50*]
> type=endpoint
> context=did-2
> disallow=all
> allow=ulaw
> 
> If this is not correct then you can only match once based on the source IP address currently.
> 
> Cheers,
> 
> -- 
> Joshua Colp
> Digium, Inc. | Senior Software Developer
> 445 Jan Davis Drive NW - Huntsville, AL 35806 - US
> Check us out at: www.digium.com & www.asterisk.org
> 
> -- 
> _____________________________________________________________________
> -- Bandwidth and Colocation Provided by http://www.api-digital.com --
> New to Asterisk? Join us for a live introductory webinar every Thurs:
>              http://www.asterisk.org/hello
> 
> asterisk-users mailing list
> To UNSUBSCRIBE or update options visit:
>  http://lists.digium.com/mailman/listinfo/asterisk-users

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.digium.com/pipermail/asterisk-users/attachments/20140902/a8865434/attachment.html>