[OpenSIPS-Users] Processing calling-name(CNAM) from PRI

[Zahid Mehmood]

Serge,
   The option is not really a secret, it was just not working as expected
due to out setup.  In Cisco documentation it is refferred to as " Buffered
Calling Name Completion
<http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/sip/configuration/15-mt/sip-config-15-mt-book/voi-sip-timer.html#GUID-3194F5C1-7995-4C1C-AD51-D14793AF0C30>"
feature [1].

Typically, you would set the following in cisco configuration:

sip-ua
    *timers buffer-invite 5000 *


[1]
http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/voice/sip/configuration/15-mt/sip-config-15-mt-book/voi-sip-timer.html



Regards,
-- 
Zahid

On Mon, Jan 11, 2016 at 6:03 AM, Serge S. Yuriev <me at nevian.org> wrote:

> Zahid,
>
> Would you mind to share us *secret* option for cisco please?
>
> On 06/01/16 18:56, Zahid Mehmood wrote:
>
>> Hi,
>>      INFO is generated in early stage.
>>
>> The information I provided in my original post was not entirely
>> accurate.  My setup was as follows:
>>
>> Carrier PRI  ----- Siemens PBX (4000)  ---(tried qsiq and primary-ni)
>> --- Cisco 3845 ---- PROXY
>>
>> After more debugging we found out that Siemens was not passing the
>> correct information in the ISDN setup messages.  Specifically, it was
>> missing the following:
>>
>> "Operation = InformationFollowing (calling_name)
>>
>> Name information in subsequent FACILITY message”
>>
>>
>> We then connected the carrier PRI directly into the media gateway and
>> that resolved the issue. Cisco gateway was already configured to act
>> similar to how Jeff described the Adtran configuration. We started
>> seeing the correct calling name as soon as the PRI was connected directly.
>>
>
> --
> Serge S. Yuriev
> Lead VoIP engineer
>
>
>
> _______________________________________________
> Users mailing list
> Users at lists.opensips.org
> http://lists.opensips.org/cgi-bin/mailman/listinfo/users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opensips.org/pipermail/users/attachments/20160111/908bebdc/attachment.htm>