SIP Mobile User Issue
Posted: 16 Dec 2013 19:06
Hi All
I have been searching the Forum hoping to find a post with a similar issue I'm facing but to no avail, but I will be glad if someone could direct me to the right post that could help solve the problem I am explaining below.
I have an OXE Configuration that includes SIP Extensions that are used internally and externally (Remote Users). For external SIP users, I am using the AVAYA (Formerly Sipera) SBC to handle and provide security for the SIP Traffic.
Internally, it works perfectly well, I am able to call the SIP Extension and make calls as well from it.
However, It doesn't work as expected externally. My registration is OK, I"m able to call any extension in the premises, but when an extension calls the external SIP Extension, it rings, when the call is answered, it is never detected by the caller, so the conversation never eventuate as the ringing tone is still delivered to the caller.
While running SIP traces, I saw the following lines:
-------------------------------------------------
Tue Oct 29 16:17:08 2013 ALARM: [CIOCom::receiveResponse] Received response is not for this entity
Tue Oct 29 16:17:08 2013 ALARM: CPU main
Tue Oct 29 16:17:08 2013 [SIPReportAlarm] Unknow alarm type '4'
Tue Oct 29 16:17:08 2013 RECEIVE MESSAGE FROM NETWORK (10.23.188.10:9521 [UDP])
----------------------utf8-----------------------
SIP/2.0 180 Ringing
From: "Room Server" <sip:158@10.23.188.101;user=phone>;tag=a7067160ed7bc8ddb701c6b28038e6ee
To: "SIP Test" <sip:185@10.23.188.101;user=phone>;tag=xbfgjzGmf4pfnI1fe3i5DaazWL4IdBCJ
CSeq: 2000597737 INVITE
Call-ID: e72d651d7f93ffc81134f99ff99792f2@10.23.188.101
Contact: "GDC Test" <sip:185@10.23.188.10:9521;ob;transport=udp>
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Via: SIP/2.0/UDP 192.168.1.10:5060;received=192.168.1.10;branch=z9hG4bK-s1632-001302653819-1--s1632-
Via: SIP/2.0/UDP 10.23.188.101;branch=z9hG4bK1462f3c99192004834b70c7f3722079f
Content-Length: 0
-------------------------------------------------
1383020232 -> Tue Oct 29 16:17:08 2013 ALARM: [CIOCom::receiveResponse] Received response is not for this entity
Tue Oct 29 16:17:08 2013 ALARM: CPU main
Tue Oct 29 16:17:08 2013 [SIPReportAlarm] Unknow alarm type '4'
Has anyone faced this issue before that could point me to the right direction? I could be missing some configuration, but am really stuck with this. OXE version is R10.1.1 - J260325a.
Cheers
Siti
I have been searching the Forum hoping to find a post with a similar issue I'm facing but to no avail, but I will be glad if someone could direct me to the right post that could help solve the problem I am explaining below.
I have an OXE Configuration that includes SIP Extensions that are used internally and externally (Remote Users). For external SIP users, I am using the AVAYA (Formerly Sipera) SBC to handle and provide security for the SIP Traffic.
Internally, it works perfectly well, I am able to call the SIP Extension and make calls as well from it.
However, It doesn't work as expected externally. My registration is OK, I"m able to call any extension in the premises, but when an extension calls the external SIP Extension, it rings, when the call is answered, it is never detected by the caller, so the conversation never eventuate as the ringing tone is still delivered to the caller.
While running SIP traces, I saw the following lines:
-------------------------------------------------
Tue Oct 29 16:17:08 2013 ALARM: [CIOCom::receiveResponse] Received response is not for this entity
Tue Oct 29 16:17:08 2013 ALARM: CPU main
Tue Oct 29 16:17:08 2013 [SIPReportAlarm] Unknow alarm type '4'
Tue Oct 29 16:17:08 2013 RECEIVE MESSAGE FROM NETWORK (10.23.188.10:9521 [UDP])
----------------------utf8-----------------------
SIP/2.0 180 Ringing
From: "Room Server" <sip:158@10.23.188.101;user=phone>;tag=a7067160ed7bc8ddb701c6b28038e6ee
To: "SIP Test" <sip:185@10.23.188.101;user=phone>;tag=xbfgjzGmf4pfnI1fe3i5DaazWL4IdBCJ
CSeq: 2000597737 INVITE
Call-ID: e72d651d7f93ffc81134f99ff99792f2@10.23.188.101
Contact: "GDC Test" <sip:185@10.23.188.10:9521;ob;transport=udp>
Allow: PRACK, INVITE, ACK, BYE, CANCEL, UPDATE, INFO, SUBSCRIBE, NOTIFY, REFER, MESSAGE, OPTIONS
Via: SIP/2.0/UDP 192.168.1.10:5060;received=192.168.1.10;branch=z9hG4bK-s1632-001302653819-1--s1632-
Via: SIP/2.0/UDP 10.23.188.101;branch=z9hG4bK1462f3c99192004834b70c7f3722079f
Content-Length: 0
-------------------------------------------------
1383020232 -> Tue Oct 29 16:17:08 2013 ALARM: [CIOCom::receiveResponse] Received response is not for this entity
Tue Oct 29 16:17:08 2013 ALARM: CPU main
Tue Oct 29 16:17:08 2013 [SIPReportAlarm] Unknow alarm type '4'
Has anyone faced this issue before that could point me to the right direction? I could be missing some configuration, but am really stuck with this. OXE version is R10.1.1 - J260325a.
Cheers
Siti