Mobile Twinning Issues- Twinned Calls Unable to Connect 3

[gswimfrk]

Hi Everybody!

The system is an IPO 8.1(81) with mobile twinning over 3 broadvox SIP trunks, all licensed.

When a caller dials our main number, the correct behavior is to ring the hunt group and the specified extensions will simultaneously ring programmed cellphones. Now when callers dial the main number, the twinning works and the system dials out and the twinned cell phone rings, however, upon answering the cell it receives dead air and no conversation can be sent or received. During the twinning process, two licenses are consumed as expected. I am able to make multiple outgoing SIP calls, thus, the SIP trunks appear to be functioning properly.

When internal calls are made from one extension to the twinned extension (1001), the user is able to pick up the twinned call via cellphone, no problem.

I have looked into the settings for call twinning in manager, all appears to be correct. The configuration has worked well previously.

Thanks for the help!!

 

[upinflamezzz]

Why not just forward hunt group calls instead of twinning?

 

[amriddle01]

Enable RTP keepalives on the trunk

 

[gswimfrk]

Upinflamezzz: Thanks for the suggestion, I have tried that previously but the employee often forgets to turn forwarding on/off. The funny thing is that it worked before.

Amriddle01: Thanks for the suggestion but it is enabled and set to what broadvox requires.

The router/firewall was swapped a few weeks ago, however, all the settings remained the same: port forwarding, ports opened, etc... I'm thinking that if users can make outbound calls, inbound calls, and twinning dials but just doesn't pass audio. Is my thinking correct? I remember twinning worked after the swap.

Thanks!

 

[amriddle01]

Just make sure SIP ALG any any other packet inspection/application layer gateways are off

 

[gswimfrk]

Definitely, it is the first thing I disabled.

 

[Ekster]

This is a classic RTP Keepalives problem, I had the exact symptoms at ione of my cutomers. However it is not set in the trunk settings but in the VOIP tab of the LAN interface you use for the SIP trunk.

Set SCOPE to RTP
Set PERIODIC TIMEOUT to (try different settings I started at 10 seconds and worked my way down)
Set INITIAL KEEPALIVES to ENABLE




+++ Divide By Cucumber Error. Please Reinstall Universe And Reboot +++

 

[gregl45]

I had the same issue. This is what Avaya had me do to solve it:
Go under the Line > VoiP tab and check the PRACK/100rel Supported box.

 

[gswimfrk]

Thanks for the ideas, guys. Still no luck.

The system already has PRACK/100rel supported checked and I have tried every RTP setting.

Any other areas I should check. It's a strange one...

Thanks!

 

[janni78]

Do a SIP Rx/Tx trace of the call and post it here.

"Trying is the first step to failure..." - Homer

 

[IPGuru]

I Am prety sure Ektster has Nailed it
Had exaqctly the same issue with off switch transferes about a monthe ago.

Play withthe keep alive settings


A Maintenance contract is essential, not a Luxury.
Do things on the cheap & it will cost you dear

 

[gswimfrk]

Thanks for all the suggestions, I have tried every combination of the RTP Keepalives and Prack/100REL settings, still no success.

I have attached the SIP TX/RX Log. I do see a "Proxy Auth Needed" and a "401 Unauthorized". Perhaps this could be problematic?



2662421mS SIP Call Rx: 17
INVITE sip:7137xxxxxx@10.0.1.201:5060 SIP/2.0
Via: SIP/2.0/UDP 208.xx.xxx.xxx;rport;branch=zxxxxxxxxxxxxxxxxxxxj
Route: <sip:7137xxxxxx@98.xxx.xxx.xx:5060>
Max-Forwards: 36
From: "CALLER ID " <sip:7136xxxxxx@208.xx.xxx.xxx>;tag=xxxxxxxxxxxxx
To: <sip:7137xxxxxx@10.0.1.201:5060>
Call-ID: 5af9886d-6d27-1232-59bd-f04da23bbb59
CSeq: 60970771 INVITE
Contact: <sip:7136xxxxxx@208.xx.xxx.xxx:5060>
User-Agent: Broadvox Fusion
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Privacy: none
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 271
P-Asserted-Identity: "CALLER ID " <sip:7136xxxxxx@208.xx.xxx.xxx>

v=0
o=FreeSWITCH 3564434183 3564434184 IN IP4 208.xx.xxx.xxx
s=FreeSWITCH
c=IN IP4 208.xx.xxx.xxx
t=0 0
m=audio 58772 RTP/AVP 0 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
2662421mS Sip: SIPDialog f5258678 created, dialogs 1
2662422mS Sip: License, Valid 1, Available 3, Consumed 0
2662424mS SIP Call Tx: 17
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 208.xx.xxx.xxx;rport;branch=zxxxxxxxxxxxxxxxxxxxj
From: "CALLER ID " <sip:7136xxxxxx@208.xx.xxx.xxx>;tag=pBggtaNZ4rt2r
To: <sip:7137xxxxxx@10.0.1.201:5060>;tag=adbd9016cf046908
Call-ID: 5af9886d-6d27-1232-59bd-f04da23bbb59
CSeq: 60970771 INVITE
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer,100rel
Server: IP Office 8.1 (81)
Content-Length: 0

2662426mS Sip: 17.1272.1 -1 SIPTrunk Endpoint(f5258678) SetRemoteRTPAddress to 208.xx.xxx.xxx:58772 (index 0)
2662432mS Sip: 17.1272.1 46 SIPTrunk Endpoint(f5259b70) received CMProceeding
2662434mS Sip: 17.1272.1 46 SIPTrunk Endpoint(f5259b70) received CMAlerting
2662435mS SIP Call Tx: 17
SIP/2.0 180 Ringing
Via: SIP/2.0/UDP 208.xx.xxx.xxx;rport;branch=zxxxxxxxxxxxxxxxxxxxj
From: "CALLER ID " <sip:7136xxxxxx@208.xx.xxx.xxx>;tag=pBggtaNZ4rt2r
To: <sip:7137xxxxxx@10.0.1.201:5060>;tag=adbd9016cf046908
Call-ID: 5af9886d-6d27-1232-59bd-f04da23bbb59
CSeq: 60970771 INVITE
Contact: "7137xxxxxx" <sip:7137xxxxxx@10.0.1.201:5060;transport=udp>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer,100rel
Server: IP Office 8.1 (81)
Content-Length: 0

2662450mS Sip: License, Valid 1, Available 3, Consumed 1
2662450mS Sip: SIPDialog f5128af8 created, dialogs 2
2662487mS Sip: 17.1280.0 47 SIPTrunk Endpoint(f5129ff0) received CMSetup
2662489mS Sip: 17.1280.0 47 SIPTrunk Endpoint(f5128af8) SetLocalRTPAddress to 10.0.1.201:49174
2662490mS SIP Call Tx: 17
INVITE sip:14153xxxxxx@208.xx.xxx.xxx SIP/2.0
Via: SIP/2.0/UDP 10.0.1.201:5060;rport;branch=z9hG4bK847d46f7c8848f6cf5873db6ce9e33e0
From: "Ida 1" <sip:007136xxxxxx@10.0.1.201>;tag=58a7b00c0243398b
To: <sip:14153xxxxxx@208.xx.xxx.xxx>
Call-ID: bxxxxxxxxxxxxxxxx4660ed955f27400
CSeq: 1398554631 INVITE
Contact: "Ida 1" <sip:007136xxxxxx@10.0.1.201:5060;transport=udp>
Authorization: Digest username="7137xxxxxx",realm="10.0.1.201",nonce="3fd2878c-f284-11e3-9af3-b10abf46ad41",response="303e4e49355859b4b9d8aa8f796f84f6",uri="sip:14153xxxxxx@208.xx.xxx.xxx",algorithm=MD5,qop=auth,nc=00000007,cnonce="84
8d1e701a63223e53e
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Content-Type: application/sdp
Supported: timer,100rel
User-Agent: IP Office 8.1 (81)
Content-Length: 259

v=0
o=UserA 1083212806 4255947321 IN IP4 10.0.1.201
s=Session SDP
c=IN IP4 10.0.1.201
t=0 0
m=audio 49174 RTP/AVP 0 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
2662547mS SIP Call Rx: 17
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.0.1.201:5060;rport=5060;branch=z9hG4bK847d46f7c8848f6cf5873db6ce9e33e0;received=98.xxx.xxx.xx
From: "Ida 1" <sip:007136xxxxxx@10.0.1.201>;tag=58a7b00c0243398b
To: <sip:14153xxxxxx@208.xx.xxx.xxx>
Call-ID: bxxxxxxxxxxxxxxxx4660ed955f27400
CSeq: 1398554631 INVITE
User-Agent: Broadvox Fusion
Content-Length: 0

2662552mS SIP Call Rx: 17
SIP/2.0 407 Proxy Authentication Required
Via: SIP/2.0/UDP 10.0.1.201:5060;rport=5060;branch=z9hG4bK847d46f7c8848f6cf5873db6ce9e33e0;received=98.xxx.xxx.xx
From: "Ida 1" <sip:007136xxxxxx@10.0.1.201>;tag=58a7b00c0243398b
To: <sip:14153xxxxxx@208.xx.xxx.xxx>;tag=Qm98U55211gNm
Call-ID: bxxxxxxxxxxxxxxxx4660ed955f27400
CSeq: 1398554631 INVITE
User-Agent: Broadvox Fusion
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Proxy-Authenticate: Digest realm="208.xx.xxx.xxx", nonce="83aeee82-f284-11e3-a980-b10abf46ad41", algorithm=MD5, qop="auth"
Content-Length: 0

2662555mS SIP Call Tx: 17
ACK sip:14153xxxxxx@208.xx.xxx.xxx SIP/2.0
Via: SIP/2.0/UDP 10.0.1.201:5060;rport;branch=z9hG4bK847d46f7c8848f6cf5873db6ce9e33e0
From: "Ida 1" <sip:007136xxxxxx@10.0.1.201>;tag=58a7b00c0243398b
To: <sip:14153xxxxxx@208.xx.xxx.xxx>;tag=Qm98U55211gNm
Call-ID: bxxxxxxxxxxxxxxxx4660ed955f27400
CSeq: 1398554631 ACK
Max-Forwards: 70
Authorization: Digest username="7137xxxxxx",realm="10.0.1.201",nonce="3fd2878c-f284-11e3-9af3-b10abf46ad41",response="3edcb5c5137b1ac846a99a8e19c0e7fe",uri="sip:14153xxxxxx@208.xx.xxx.xxx",algorithm=MD5,qop=auth,nc=00000008,cnonce="68
321607177d0764d48
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
User-Agent: IP Office 8.1 (81)
Content-Length: 0

2662557mS SIP Call Tx: 17
INVITE sip:14153xxxxxx@208.xx.xxx.xxx SIP/2.0
Via: SIP/2.0/UDP 10.0.1.201:5060;rport;branch=zxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx2
From: "Ida 1" <sip:007136xxxxxx@10.0.1.201>;tag=58a7b00c0243398b
To: <sip:14153xxxxxx@208.xx.xxx.xxx>
Call-ID: bxxxxxxxxxxxxxxxx4660ed955f27400
CSeq: 1398554632 INVITE
Contact: "Ida 1" <sip:007136xxxxxx@10.0.1.201:5060;transport=udp>
Max-Forwards: 70
Proxy-Authorization: Digest username="7137xxxxxx",realm="208.xx.xxx.xxx",nonce="83aeee82-f284-11e3-a980-b10abf46ad41",response="f95dcf93df901d9fc6b77df17b1b4da3",uri="sip:14153xxxxxx@208.xx.xxx.xxx",algorithm=MD5,qop=auth,nc=00000001,
nonce="7bebc1e08ff47a078051
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer,100rel
User-Agent: IP Office 8.1 (81)
Content-Type: application/sdp
Content-Length: 259

v=0
o=UserA 1083212806 4255947321 IN IP4 10.0.1.201
s=Session SDP
c=IN IP4 10.0.1.201
t=0 0
m=audio 49174 RTP/AVP 0 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
2662613mS SIP Call Rx: 17
SIP/2.0 100 Trying
Via: SIP/2.0/UDP 10.0.1.201:5060;rport=5060;branch=zxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx2;received=98.xxx.xxx.xx
From: "Ida 1" <sip:007136xxxxxx@10.0.1.201>;tag=58a7b00c0243398b
To: <sip:14153xxxxxx@208.xx.xxx.xxx>
Call-ID: bxxxxxxxxxxxxxxxx4660ed955f27400
CSeq: 1398554632 INVITE
User-Agent: Broadvox Fusion
Content-Length: 0

2666480mS SIP Call Rx: 17
SIP/2.0 183 Session Progress
Via: SIP/2.0/UDP 10.0.1.201:5060;rport=5060;branch=zxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx2;received=98.xxx.xxx.xx
From: "Ida 1" <sip:007136xxxxxx@10.0.1.201>;tag=58a7b00c0243398b
To: <sip:14153xxxxxx@208.xx.xxx.xxx>;tag=S6UtZU79UKXtB
Call-ID: bxxxxxxxxxxxxxxxx4660ed955f27400
CSeq: 1398554632 INVITE
Contact: <sip:14153xxxxxx@208.xx.xxx.xxx:5060;transport=udp>
User-Agent: Broadvox Fusion
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 224

v=0
o=FreeSWITCH 3564561467 3564561468 IN IP4 208.xx.xxx.xxx
s=FreeSWITCH
c=IN IP4 208.xx.xxx.xxx
t=0 0
m=audio 27180 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
2666481mS Sip: 17.1280.0 47 SIPTrunk Endpoint(f5128af8) SetRemoteRTPAddress to 208.xx.xxx.xxx:27180 (index 0)
2667346mS Sip: SIPDialog f5194438 created, dialogs 3
2667347mS SIP Reg/Opt Tx: 17
OPTIONS sip:10.0.1.201 SIP/2.0
Via: SIP/2.0/UDP 10.0.1.201:5060;rport;branch=z9hG4bKe407397a07879835a4157e2ce645c9f7
From: <sip:10.0.1.201>;tag=fa46cabfab418e99
To: <sip:10.0.1.201>
Call-ID: b42f910c83e816a3e25429022566fcb1
CSeq: 1271043617 OPTIONS
Contact: <sip:10.0.1.201:5060;transport=udp>
Max-Forwards: 70
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer
User-Agent: IP Office 8.1 (81)
Content-Length: 0

2667402mS SIP Reg/Opt Rx: 17
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.1.201:5060;rport=5060;branch=z9hG4bKe407397a07879835a4157e2ce645c9f7;received=98.xxx.xxx.xx
From: <sip:10.0.1.201>;tag=fa46cabfab418e99
To: <sip:10.0.1.201>;tag=1FFt6N9p8Qr6a
Call-ID: b42f910c83e816a3e25429022566fcb1
CSeq: 1271043617 OPTIONS
Contact: <sip:208.xx.xxx.xxx>
User-Agent: Broadvox Fusion
Accept: application/sdp
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Content-Length: 0

2669017mS Sip: SIPDialog f51684d8 created, dialogs 4
2669019mS SIP Reg/Opt Tx: 17
REGISTER sip:10.0.1.201 SIP/2.0
Via: SIP/2.0/UDP 10.0.1.201:5060;rport;branch=z9hG4bK3974828d8690c5f95d63e85da9b9a9ef
From: <sip:7137xxxxxx@10.0.1.201>;tag=a541096f0d942b7e
To: <sip:7137xxxxxx@10.0.1.201>
Call-ID: c0e4343e78ac9d63dd5f08ddd090fe0f
CSeq: 621395595 REGISTER
Contact: "Unknown" <sip:7137xxxxxx@10.0.1.201:5060;transport=udp>
Expires: 3600
Proxy-Authorization: Digest username="7137xxxxxx",realm="208.xx.xxx.xxx",nonce="83aeee82-f284-11e3-a980-b10abf46ad41",response="ed4de4c6b9bf4c8f557090ca6bb3bbca",uri="sip:10.0.1.201",algorithm=MD5,qop=auth,nc=00000002,cnonce="4c0e6636
042c17f463a
Max-Forwards: 70
User-Agent: IP Office 8.1 (81)
Supported: timer,100rel
Content-Length: 0

2669082mS SIP Reg/Opt Rx: 17
SIP/2.0 401 Unauthorized
Via: SIP/2.0/UDP 10.0.1.201:5060;rport=5060;branch=z9hG4bK3974828d8690c5f95d63e85da9b9a9ef;received=98.xxx.xxx.xx
From: <sip:7137xxxxxx@10.0.1.201>;tag=a541096f0d942b7e
To: <sip:7137xxxxxx@10.0.1.201>;tag=H03626pFt6vHm
Call-ID: c0e4343e78ac9d63dd5f08ddd090fe0f
CSeq: 621395595 REGISTER
User-Agent: Broadvox Fusion
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces

http://WWW-Authenticate:

Digest realm="10.0.1.201", nonce="8793e962-f284-11e3-ad33-b10abf46ad41", algorithm=MD5, qop="auth"
Content-Length: 0

2669084mS SIP Reg/Opt Tx: 17
REGISTER sip:10.0.1.201 SIP/2.0
Via: SIP/2.0/UDP 10.0.1.201:5060;rport;branch=z9hG4bK5602c32d75cbc2c79b38eda6adfb69b9
From: <sip:7137xxxxxx@10.0.1.201>;tag=a541096f0d942b7e
To: <sip:7137xxxxxx@10.0.1.201>
Call-ID: c0e4343e78ac9d63dd5f08ddd090fe0f
CSeq: 621395596 REGISTER
Contact: "Unknown" <sip:7137xxxxxx@10.0.1.201:5060;transport=udp>
Expires: 3600
Authorization: Digest username="7137xxxxxx",realm="10.0.1.201",nonce="8793e962-f284-11e3-ad33-b10abf46ad41",response="6e24034147b09410f25ee08ca43f52c4",uri="sip:10.0.1.201",algorithm=MD5,qop=auth,nc=00000001,cnonce="ed6d4c6507356478cf
8
Max-Forwards: 70
User-Agent: IP Office 8.1 (81)
Supported: timer,100rel
Content-Length: 0

2669165mS SIP Reg/Opt Rx: 17
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.1.201:5060;rport=5060;branch=z9hG4bK5602c32d75cbc2c79b38eda6adfb69b9;received=98.xxx.xxx.xx
From: <sip:7137xxxxxx@10.0.1.201>;tag=a541096f0d942b7e
To: <sip:7137xxxxxx@10.0.1.201>;tag=Kjpr6vrpmr9pB
Call-ID: c0e4343e78ac9d63dd5f08ddd090fe0f
CSeq: 621395596 REGISTER
Contact: <sip:7137xxxxxx@10.0.1.201:5060;transport=udp>;expires=60
Date: Thu, 12 Jun 2014 22:54:37 GMT
User-Agent: Broadvox Fusion
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Supported: timer, path, replaces
Content-Length: 0

2669166mS Sip: SIP Line (17) parameter 7137xxxxxx registered, expires in 30 seconds (interval 60)
2669166mS Sip: SIPDialog f51684d8 deleted, dialogs 3
2672402mS Sip: SIPDialog f5194438 deleted, dialogs 2
2673766mS SIP Call Rx: 17
SIP/2.0 200 OK
Via: SIP/2.0/UDP 10.0.1.201:5060;rport=5060;branch=zxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx2;received=98.xxx.xxx.xx
From: "Ida 1" <sip:007136xxxxxx@10.0.1.201>;tag=58a7b00c0243398b
To: <sip:14153xxxxxx@208.xx.xxx.xxx>;tag=S6UtZU79UKXtB
Call-ID: bxxxxxxxxxxxxxxxx4660ed955f27400
CSeq: 1398554632 INVITE
Contact: <sip:14153xxxxxx@208.xx.xxx.xxx:5060;transport=udp>
User-Agent: Broadvox Fusion
Allow: INVITE, ACK, BYE, CANCEL, OPTIONS, MESSAGE, INFO, UPDATE, REGISTER, REFER, NOTIFY
Require: timer
Supported: timer, path, replaces
Allow-Events: talk, hold, conference, refer
Session-Expires: 120;refresher=uac
Min-SE: 120
Content-Type: application/sdp
Content-Disposition: session
Content-Length: 224

v=0
o=FreeSWITCH 3564561467 3564561468 IN IP4 208.xx.xxx.xxx
s=FreeSWITCH
c=IN IP4 208.xx.xxx.xxx
t=0 0
m=audio 27180 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=ptime:20
2673768mS SIP Call Tx: 17
ACK sip:14153xxxxxx@208.xx.xxx.xxx:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 10.0.1.201:5060;rport;branch=z9hG4bKd3ad3159db70b837bcbe7cfc1a1e0bd4
From: "Ida 1" <sip:007136xxxxxx@10.0.1.201>;tag=58a7b00c0243398b
To: <sip:14153xxxxxx@208.xx.xxx.xxx>;tag=S6UtZU79UKXtB
Call-ID: bxxxxxxxxxxxxxxxx4660ed955f27400
CSeq: 1398554632 ACK
Max-Forwards: 70
Authorization: Digest username="7137xxxxxx",realm="10.0.1.201",nonce="8793e962-f284-11e3-ad33-b10abf46ad41",response="2774d8d1317ff342f586a2fc86989ef2",uri="sip:14153xxxxxx@208.xx.xxx.xxx:5060;transport=udp",algorithm=MD5,qop=auth,nc=
0000002,cnonce="ca019b87eb536f809d71
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
User-Agent: IP Office 8.1 (81)
Content-Length: 0

2673797mS Sip: 17.1272.1 46 SIPTrunk Endpoint(f5259b70) received CMConnect
2673797mS Sip: 17.1272.1 46 SIPTrunk Endpoint(f5258678) SetLocalRTPAddress to 10.0.1.201:49176
2673799mS SIP Call Tx: 17
SIP/2.0 200 OK
Via: SIP/2.0/UDP 208.xx.xxx.xxx;rport;branch=zxxxxxxxxxxxxxxxxxxxj
From: "CALLER ID " <sip:7136xxxxxx@208.xx.xxx.xxx>;tag=pBggtaNZ4rt2r
To: <sip:7137xxxxxx@10.0.1.201:5060>;tag=adbd9016cf046908
Call-ID: 5af9886d-6d27-1232-59bd-f04da23bbb59
CSeq: 60970771 INVITE
Contact: "7137xxxxxx" <sip:7137xxxxxx@10.0.1.201:5060;transport=udp>
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer,100rel
Server: IP Office 8.1 (81)
Content-Type: application/sdp
Content-Length: 211

v=0
o=UserA 2378928503 110295697 IN IP4 10.0.1.201
s=Session SDP
c=IN IP4 10.0.1.201
t=0 0
m=audio 49176 RTP/AVP 0 101
a=rtpmap:0 PCMU/8000
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv
2673801mS Sip: 17.1280.0 47 SIPTrunk Endpoint(f5129ff0) received CMFacility
2673802mS Sip: 17.1272.1 46 SIPTrunk Endpoint(f5259b70) received CMFacility
2673811mS Sip: 17.1280.0 47 SIPTrunk Endpoint(f5129ff0) received CMConnectAck
2673858mS SIP Call Rx: 17
ACK sip:7137xxxxxx@10.0.1.201:5060;transport=udp SIP/2.0
Via: SIP/2.0/UDP 208.xx.xxx.xxx;rport;branch=z9hG4bKeXtmvHXp1USeH
Max-Forwards: 70
From: "CALLER ID " <sip:7136xxxxxx@208.xx.xxx.xxx>;tag=pBggtaNZ4rt2r
To: <sip:7137xxxxxx@10.0.1.201:5060>;tag=adbd9016cf046908
Call-ID: 5af9886d-6d27-1232-59bd-f04da23bbb59
CSeq: 60970771 ACK
Contact: <sip:7136xxxxxx@208.xx.xxx.xxx:5060>
Content-Length: 0


********** Warning: Logging to Screen Stopped **********

 

[gswimfrk]

Thanks for all the help guys! I finally was able to figure out the issue after talking with broadvox. The issue was the setting under "Network Topology". Previously the system was placed under "Open Internet" and has worked fine behind a router. According to the folks at broadvox, this setting is a little iffy and does often cause problems with Twinning. So in our office with the IPO behind a Cisco Router, the setting that was successful was a blocking firewall.

Does any know what Avaya defines each as each of these settings? ie: open internet, symmetrical firewall, full cone nat, etc.

Thanks!

 

[janni78]

Think the issue was that you were telling you SIP provider to send the RTP to a local address.

In the Network Topology you can define what IP it should present to the SIP provider if the PBX is behind a firewall, probably why changing it to Blocking Firewall solved the issue.

2662557mS SIP Call Tx: 17
INVITE sip:14153xxxxxx@208.xx.xxx.xxx SIP/2.0
Via: SIP/2.0/UDP 10.0.1.201:5060;rport;branch=zxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx2
From: "Ida 1" <sip:007136xxxxxx@10.0.1.201>;tag=58a7b00c0243398b
To: <sip:14153xxxxxx@208.xx.xxx.xxx>
Call-ID: bxxxxxxxxxxxxxxxx4660ed955f27400
CSeq: 1398554632 INVITE
Contact: "Ida 1" <sip:007136xxxxxx@10.0.1.201:5060;transport=udp>
Max-Forwards: 70
Proxy-Authorization: Digest username="7137xxxxxx",realm="208.xx.xxx.xxx",nonce="83aeee82-f284-11e3-a980-b10abf46ad41",response="f95dcf93df901d9fc6b77df17b1b4da3",uri="sip:14153xxxxxx@208.xx.xxx.xxx",algorithm=MD5,qop=auth,nc=00000001,
nonce="7bebc1e08ff47a078051
Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, NOTIFY, INFO, UPDATE
Supported: timer,100rel
User-Agent: IP Office 8.1 (81)
Content-Type: application/sdp
Content-Length: 259

v=0
o=UserA 1083212806 4255947321 IN IP4 10.0.1.201
s=Session SDP
c=IN IP4 10.0.1.201
t=0 0
m=audio 49174 RTP/AVP 0 18 101
a=rtpmap:0 PCMU/8000
a=rtpmap:18 G729/8000
a=fmtp:18 annexb=no
a=rtpmap:101 telephone-event/8000
a=fmtp:101 0-15
a=sendrecv

"Trying is the first step to failure..." - Homer

 

[gswimfrk]

I did notice that when I was looking through the logs. I corrected the issue prior to making changes in the network topology section. With a correct IP address and a correct topology setting the router twinning was able to work.

I'm still very surprised/confused why twinning worked before.

Thanks for everyone's help!