On Sun, May 23, 2010 at 7:41 AM, Scott Lawrence <xmlsc...@gmail.com> wrote:
> On 2010-05-23 4:35, Sven Evensen wrote:
>>
>> We are running sipX 4.0.4 in Amazon EC2 Singapore with an ITSP located
>> in Hong Kong.
>>
>> When I place an incoming call to a soft phone, when the soft phone
>> answers, 200 OK
>>
>> propagates back to the ITSP. But it is rejected (thus no OK), the rest
>> of the call times out
>>
>> and fail.
>>
>> See below reply from ITSP
>>
>> ----------
>>
>> Sven,
>>
>> Our proxy has dropped this "200 OK" as it is not able to retrieve an
>> address from the Record-Route header:
>>
>> repr(e)=ValueError("SipAddress: cannot find name-addr or addr-spec;
>> input='<sip:175.41.131.35:5060;lr;sipXecs-rs=*auth~.*from~ZDVmNDJmNzRhNDg0OWNiOTk2YjY5Mz
>>
>> ZhZDY0MjIxMDVv.900_ntap*id~MzIwMTctMQ``!8bb4fd03a18ef243d78130652f1a3979;x-sipX-done>'",)
>>
>> tid=('3261', 'z9hG4bKf68db4b26df5665097f7ba27cc3ced5a',
>>
>> ('172.16.19.218', 5061), 'INVITE')
>>
>> As you can see below, we are getting debug information in the
>> Record-Route header we get back from your address:
>>
>> Record-Route:
>>
>> <sip:175.41.131.35:5060;lr;sipXecs-rs=%2Aauth%7E.%2Afrom%7EZDVmNDJmNzRhNDg0OWNiOTk2YjY5MzZhZDY0MjIxMDVv.900_ntap%2Aid%7EMzIwMTctMQ%60%60%218bb4fd03a18ef243d78130652f1a3979;x-sipX-done>
>>
>> Is it possible to exclude all debug information from the Record-Route
>> header and construct it as:
>>
>> <sip:175.41.131.35:5060;lr>
>>
>> ----------
>>
>
> The Record-Route that sipXecs is adding is perfectly ok - the parser at
> the ITSP is flawed if it cannot parse it.
>
> The extra information in parameters that sipXecs has put into the value
> is there to enable various dialog-sensitive features (not debugging).
> There's no way to disable that information being included.
>>
>> On another sipX installation we have with exact same setup (different
>> ITSP), the record-route look like:
>>
>> Record-Route: <sip:79.135.125.179;lr=on;did=65c.7d670942>
>>
>>
> No, it's not the exact same setup, since that header would not have been
> inserted by sipXecs (providing a value for the 'lr' parameter is
> incorrect, and sipXecs does not use a 'did' parameter).
>
> _______________________________________________
> sipx-users mailing list sipx-users@list.sipfoundry.org
> List Archive: http://list.sipfoundry.org/archive/sipx-users
> Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
> sipXecs IP PBX -- http://www.sipfoundry.org/
>
SipXbridge does not send Record route headers to the ITSP. I strongly
suspect sipxbridge is being bypassed. Make sure that signaling is
being sent to Port 5080.
Ranga
--
M. Ranganathan
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
sipXecs IP PBX -- http://www.sipfoundry.org/
