Hi All
I need help with this issue.
I configured a SIP Trunk with the SBC on the DMZ, and I am having problems pushing calls through the SIP Trunk. Whenever the OXE receives the 100 [Trying] message from the SBC [actually from the SIP extgw], the OXE responds with the CANCEL message, but the SBC still progresses the call and it rings on the called party.
I am suspecting an interworking issue and I am wondering whether any of you guys can help me understand the traces. I know that the OXE is sending the CANCEL signal but I need to know why. I have done some traces, and in the call trace, the CPU stated that the cause of disconnection is RECOVERY TIME EXPIRY.
I am attaching the traces, can someone please help understand why the OXE is sending the CANCEL signal.
I look forward to favorable responses.
Cheers
Siti
OXE with SIPERA SBC
OXE with SIPERA SBC
Every adversity has within it a seed of an equivalent or greater benefit....
Re: OXE with SIPERA SBC
Attached are the traces in a compressed file.
You do not have the required permissions to view the files attached to this post.
Every adversity has within it a seed of an equivalent or greater benefit....
Re: OXE with SIPERA SBC
IP Addresses:
OXE - 192.168.30.150
SBC internal interface (LAN) - 192.168.30.6
SBC external interface (WAN) - 192.168.200.6
OXE - 192.168.30.150
SBC internal interface (LAN) - 192.168.30.6
SBC external interface (WAN) - 192.168.200.6
Every adversity has within it a seed of an equivalent or greater benefit....
Re: OXE with SIPERA SBC
Got it working now, I increased Timer 310 in SIP Trunk COS to 1100. This timer handles a timeout that is used incase the called party does not respond quickly.
Every adversity has within it a seed of an equivalent or greater benefit....
